feat: add sensitive Declarative setting example #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It would be nice to have a new second button in addition to "Check Initial Value" to read and write the sensitive value of declarative setting field, so we can always easy test it in future. |
andrey18106
force-pushed
the
feat/add-sensitive-declarative-setting
branch
from
0ed7ce6 to
17f039d
Compare
Signed-off-by: Andrey Borysenko <[email protected]>
andrey18106
force-pushed
the
feat/add-sensitive-declarative-setting
branch
from
17f039d to
4257b83
Compare
andrey18106
force-pushed
the
feat/add-sensitive-declarative-setting
branch
from
cd5b6f5 to
b203613
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add sensitive field example (requires cloud-py-api/nc_py_api#361).